Methods, systems, and devices for configuring a federated blockchain network

ABSTRACT

Aspects of the subject disclosure may include, for example, obtaining, from a user device, a master-slave agreement and a first network configuration for a federated blockchain network, transmitting to a cloud service provider (CSP) node the first network configuration, generating first credentials, and transmitting the first credentials to the CSP node. The CSP node configures a first group of blockchain nodes according to the first network configuration and the first credentials. Further embodiments include transmitting the first credentials to a public server that sends it to a public blockchain node and an indication to generate a portion of the federated blockchain network. The public blockchain node configures a second group of blockchain nodes according to a second network configuration based on a public blockchain smart contract. The federated blockchain network comprises the first group of blockchain nodes and the second group of blockchain nodes. Other embodiments are disclosed.

FIELD OF THE DISCLOSURE

The subject disclosure relates to methods, systems, and devices for configuring a federated blockchain network.

BACKGROUND

Conventional blockchain networks can comprise either public blockchain networks or private blockchain networks. Public blockchain networks have a decentralized architecture that allow for performing secured transactions in which any number of users can utilize. In contrast, private blockchain networks regulates access by providing permission to select users to utilize the private blockchain.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

FIG. 1 is a block diagram illustrating an exemplary, non-limiting embodiment of a communications network in accordance with various aspects described herein.

FIGS. 2A-2C are block diagrams illustrating example, non-limiting embodiments of systems functioning within the communication network of FIG. 1 in accordance with various aspects described herein.

FIG. 2D depicts an illustrative embodiment of a method in accordance with various aspects described herein.

FIG. 3 is a block diagram illustrating an example, non-limiting embodiment of a virtualized communication network in accordance with various aspects described herein.

FIG. 4 is a block diagram of an example, non-limiting embodiment of a computing environment in accordance with various aspects described herein.

FIG. 5 is a block diagram of an example, non-limiting embodiment of a mobile network platform in accordance with various aspects described herein.

FIG. 6 is a block diagram of an example, non-limiting embodiment of a communication device in accordance with various aspects described herein.

DETAILED DESCRIPTION

The subject disclosure describes, among other things, illustrative embodiments for obtaining, by a processing system including a processor, from a user device, a master-slave agreement for a federated blockchain network and obtaining, by the processing system, a first network configuration for the federated blockchain network. Further embodiments include transmitting, by the processing system, to a cloud service provider (CSP) node, the first network configuration. Additional embodiments include generating, by the processing system, first credentials, and transmitting, by the processing system, the first credentials to the CSP node. The CSP node configures a first group of blockchain nodes according to the first network configuration and the first credentials. Also, the embodiments include transmitting, by the processing system, the first credentials to a public server. The public server sends, to a public blockchain node, the first credentials and an indication to generate a portion of the federated blockchain network. The public blockchain node configures a second group of blockchain nodes according to a second network configuration based on a public blockchain smart contract. The federated blockchain network comprises the first group of blockchain nodes and the second group of blockchain nodes. Other embodiments are described in the subject disclosure.

One or more aspects of the subject disclosure include a method. The method can comprise obtaining, by a processing system including a processor, from a user device, a master-slave agreement for a federated blockchain network and obtaining, by the processing system, a first network configuration for the federated blockchain network. Further, the method can comprise transmitting, by the processing system, to a CSP node, the first network configuration, generating, by the processing system, first credentials, and transmitting, by the processing system, the first credentials to the CSP node. The CSP node can configure a first group of blockchain nodes according to the first network configuration and the first credentials. In addition, the method can comprise transmitting, by the processing system, the first credentials to a public server. The public server can send, to a public blockchain node, the first credentials and an indication to generate a portion of the federated blockchain network. The public blockchain node can configure a second group of blockchain nodes according to a second network configuration based on a public blockchain smart contract. The federated blockchain network can comprise the first group of blockchain nodes and the second group of blockchain nodes.

One or more aspects of the subject disclosure include a device, comprising a processing system including a processor, and a memory that stores executable instructions that, when executed by the processing system, facilitate performance of operations. The operations can comprise receiving a first credentials and receiving a first network configuration from an access node for a federated blockchain network, and configuring a first group of blockchain nodes according to the first network configuration. Further, the operations can comprise receiving a second network configuration from a public blockchain node, and configuring the first group of blockchain nodes according to the second network configuration. The public blockchain node can configure a second group of blockchain nodes according to the second network configuration. The federated blockchain network can comprise the first group of blockchain nodes and the second group of blockchain nodes.

One or more aspects of the subject disclosure include a machine-readable storage device, comprising executable instructions that, when executed by a processing system including a processor, facilitate performance of operations. The operations can comprise receiving an indication from a public server to generate a portion of a federated blockchain network according to a public blockchain smart contract, and configuring a first group of blockchain nodes according to a first network configuration based on the public blockchain smart contract. Further, the operations can comprise transmitting the first network configuration to a CSP node. The CSP node can configure a second group of blockchain nodes according to the first network configuration. The federated blockchain network can comprise the first group of blockchain nodes and the second group of block chain nodes.

Referring now to FIG. 1, a block diagram is shown illustrating an example, non-limiting embodiment of a communications network 100 in accordance with various aspects described herein. For example, communications network 100 can facilitate in whole or in part configuring CSP nodes and public blockchain nodes for a federated blockchain network. In particular, a communications network 125 is presented for providing broadband access 110 to a plurality of data terminals 114 via access terminal 112, wireless access 120 to a plurality of mobile devices 124 and vehicle 126 via base station or access point 122, voice access 130 to a plurality of telephony devices 134, via switching device 132 and/or media access 140 to a plurality of audio/video display devices 144 via media terminal 142. In addition, communication network 125 is coupled to one or more content sources 175 of audio, video, graphics, text and/or other media. While broadband access 110, wireless access 120, voice access 130 and media access 140 are shown separately, one or more of these forms of access can be combined to provide multiple access services to a single client device (e.g., mobile devices 124 can receive media content via media terminal 142, data terminal 114 can be provided voice access via switching device 132, and so on).

The communications network 125 includes a plurality of network elements (NE) 150, 152, 154, 156, etc. for facilitating the broadband access 110, wireless access 120, voice access 130, media access 140 and/or the distribution of content from content sources 175. The communications network 125 can include a circuit switched or packet switched network, a voice over Internet protocol (VoIP) network, Internet protocol (IP) network, a cable network, a passive or active optical network, a 4G, 5G, or higher generation wireless access network, WIMAX network, UltraWideband network, personal area network or other wireless access network, a broadcast satellite network and/or other communications network.

In various embodiments, the access terminal 112 can include a digital subscriber line access multiplexer (DSLAM), cable modem termination system (CMTS), optical line terminal (OLT) and/or other access terminal. The data terminals 114 can include personal computers, laptop computers, netbook computers, tablets or other computing devices along with digital subscriber line (DSL) modems, data over coax service interface specification (DOCSIS) modems or other cable modems, a wireless modem such as a 4G, 5G, or higher generation modem, an optical modem and/or other access devices.

In various embodiments, the base station or access point 122 can include a 4G, 5G, or higher generation base station, an access point that operates via an 802.11 standard such as 802.11n, 802.11ac or other wireless access terminal. The mobile devices 124 can include mobile phones, e-readers, tablets, phablets, wireless modems, and/or other mobile computing devices.

In various embodiments, the switching device 132 can include a private branch exchange or central office switch, a media services gateway, VoIP gateway or other gateway device and/or other switching device. The telephony devices 134 can include traditional telephones (with or without a terminal adapter), VoIP telephones and/or other telephony devices.

In various embodiments, the media terminal 142 can include a cable head-end or other TV head-end, a satellite receiver, gateway or other media terminal 142. The display devices 144 can include televisions with or without a set top box, personal computers and/or other display devices.

In various embodiments, the content sources 175 include broadcast television and radio sources, video on demand platforms and streaming video and audio services platforms, one or more content data networks, data servers, web servers and other content servers, and/or other sources of media.

In various embodiments, the communications network 125 can include wired, optical and/or wireless links and the network elements 150, 152, 154, 156, etc. can include service switching points, signal transfer points, service control points, network gateways, media distribution hubs, servers, firewalls, routers, edge devices, switches and other network nodes for routing and controlling communications traffic over wired, optical and wireless links as part of the Internet and other public networks as well as one or more private networks, for managing subscriber access, for billing and network management and for supporting other network functions.

FIGS. 2A-2C are block diagrams illustrating example, non-limiting embodiments of systems functioning within the communication network of FIG. 1 in accordance with various aspects described herein. Referring to FIG. 2A, in one or more embodiments, the system 200 comprises a user device 204 operated by a user 202, the user device 204 can be communicatively coupled to an access node 206 over a communication network. The user device 204 can be, but not limited to, a mobile device such as a mobile phone, tablet computer, laptop computer, smartwatch, wearable device, as well as a desktop computer, or any other computing device. Further, the system 200 comprises a first CSP node 208 a, a second CSP node 210 a, a public server 212, and a public blockchain node 214 a, each of which are communicatively coupled to each other and the access node 206 over a communication network. Further, the system 200 includes a first CSP network 208 comprising a first group of CSP nodes 208 a, 208 b, 208 c all of which are communicatively coupled with each other over a communication network and the system 200 includes a second CSP network 210 comprising a second group of CSP nodes 210 a, 210 b, 210 c all of which are communicatively coupled with each other over a communication network. In addition, the system 200 includes a public blockchain network 214 comprising a group of blockchain nodes 214 a, 214 b, 214 c all of which are communicatively coupled with each other over a communication network. Each communication network described herein can be a wired communication network, a wireless communication network, or a combination of a wired communication network and a wireless communication network.

In one or more embodiments, the system 200 comprises a federated blockchain network, which in turn comprises a private blockchain including the first group of CSP nodes 208 a, 208 b, 208 c of the first CSP network 208 and second group of CSP nodes 210 a, 210 b, 210 c of the second CSP network 210 as well as a public blockchain including the public blockchain nodes 214 a, 214 b, 214 c of the public blockchain network 214.

Conventional public blockchain networks enable uncensored adjudication of (secured) transactions and appending the transactions to a shared, public ledger. Further, the decentralized architecture of a public blockchain network provides benefits such as persistence, immutability, and finality of the secured transactions added to the public ledger. However, public computational consensus algorithms that secure the public blockchain network (e.g. proof of work, proof of intelligence, etc.) can require each or any one of the public blockchain nodes are adequately compensated for use of their own computational resources. Further, a public blockchain nodes of a public blockchain network are vulnerable to cyberattacks such as denial service and transaction spam. In addition, a public blockchain network may not provide availability to all potential users due to its permissiveness to allow any user to utilize it or offer adequate disaster recovery due to its decentralized architecture.

Conventional private blockchain networks can be implemented by one CSP. Disaster recovery in a private blockchain network can be more robust than a private blockchain network due to its more centralized architecture and high availability can be provided by a private blockchain network by regulating user access to it. However, a private blockchain network is vulnerable to sabotage by a bad actor within the entity operating the private blockchain network. Thus, a private blockchain may not as robust a public blockchain in securing transactions. Further, a user may not trust a private blockchain network due to its more centralized architecture as well as due to lack of trust with the CSP based on previous reports of lack of security or bad reputation (e.g. a CSP had a data breach from hackers).

In one or more embodiments, a federated blockchain network comprises blockchain nodes 208 a, 208 b, 208 c, 210 a, 210 b, 210 c from more than one CSP network 208, 210 as well as blockchain nodes 214 a, 214 b, 214 c from a public blockchain network 214. Further, the federated blockchain network can include an access node 206 that is operated by a stewarding entity that interacts with a user device 204, each of the CSP networks 208, 210, and the public blockchain network 214. The federated blockchain network regulates user access to avoid users exhausting the computational resources of the federated blockchain network. Further, the federated blockchain network is less vulnerable to cyberattacks than a conventional public blockchain network because its resources span not only the public blockchain nodes 214 a, 214 b, 214 c but also CSP nodes 208 a, 208 b, 208 c, 210 a, 210 b, 210 c, which can provide security from public cyberattacks. Also, the federated blockchain network has a more decentralized architecture by spanning more than one CSP than a conventional private blockchain network which is constrain to one CSP, such that the federated blockchain network is less vulnerable to attack from a bad actor. In addition, the federated blockchain network has more trust than a private blockchain network due to its decentralized architecture because a user can select CSPs that the user trusts to provide portions of the federated blockchain network.

In one or more embodiments, the user 202 can select a group of (trusted) CSPs and a public blockchain network to implement portions of the federated blockchain network through the user device 204. That is, a user interface can be provided by the access node 206 to the user device 204 with a selectable list of CSPs and public blockchain networks such that the user can select the group of CSPs and select the public blockchain network to implement portions of the federated blockchain network from the selectable list of CSPs and public blockchain networks. Further, the access node 206 can provide a master-slave agreement (MSA) for each of the selected CSPs and selected public blockchain network (if applicable). The intermediary entity operating the access node 206 can have an MSA in place with each of the CSPs to re-sell or provision blockchain services in the federated blockchain. Further, the intermediate entity can leverage these existing MSA to provide the blockchain nodes to a user who is procuring a federated blockchain network that is comprised of the blockchain nodes from a diverse, trusted collection of CSPs.

In one or more embodiments, the user 202 can provide technical configurations for the federated blockchain network including a first network configuration to the access node 206 via the user device 204. The technical configurations can also include business network definitions, network models, scripts, access control lists, and query files. A business network definition includes a network model, a script, access control lists, and query files. A network model can define or otherwise characterize assets, participants and transactions for the federated blockchain network. A script can be used to implement one or more transactions of the federated blockchain network. The access control lists provides a list of users that have permission to utilize the federated blockchain network to prevent oversaturation (and consequently exhaustion of computational resources) of the federated blockchain network from too many users. Query files can define the different queries that can be provided/implemented in the federated blockchain network.

In one or more embodiments, the access node 206 can establish a master account for each selected CSP on itself and establish a slave account for each CSP on a respective CSP node 208 a, 210 a. Further, the access node 206 can generate first credentials for each of CSP and transmits the first credentials to a CSP node 208 a, 210 a for each CSP network. First credentials can comprise usernames and passwords. Also, each CSP node 208 a, 210 a can configure their respective CSP nodes 208 a, 208 b, 208 c, 210 a, 210 b, 210 c according to the first network configuration and the first credentials. In addition, the access node 206 can provide the first credentials to the public server 212.

In one or more embodiments, in response to the public server 212 receiving the first credentials, the public blockchain node 214 a is provided a notification, by the public server 212, to generate a portion of the federated blockchain network and that the first credentials are stored at the public server 212. Such a notification causes the public blockchain node 214 a to configure the public blockchain nodes 214 a, 214 b, 214 c according to a public blockchain smart contract. Further, the public blockchain smart contract comprises a second network configuration. Also, the public blockchain nodes 214 a can generate second credentials. In addition, the public blockchain node 214 a can configure public blockchain nodes 214 a, 214 b, 214 c according to the second network configuration using the second credentials.

In one or more embodiments, the public blockchain node 214 a can access CSP node 208 a, 210 a using the first credentials and provides instructions to each CSP node 208 a, 210 a to adjust the first credentials to the second credentials. Further, the public blockchain node 214 a can provide the second network configuration. In addition, the providing of the second network configuration can include providing the network model, scripts, access control rules, and query definitions. CSP node 208 a can configure CSP nodes 208 a, 208 b, 208 c according to the second network configuration from the public blockchain node 214 a using the second credentials. Also, CSP node 210 a can configure CSP nodes 210 a, 210 b, 210 c according to the second network configuration from the public blockchain node 214 a using the second credentials. Having the CSP nodes use the second credentials in configuring portions of the federated blockchain network generated by the public blockchain node 214 a instead of the first credentials generated by private blockchain components can mitigate the federated blockchain network vulnerability to attacks from bad actors within the CSPs as any bad actors would not have access to the second credentials.

In some embodiments, the configuring of the CSP nodes 208 a, 208 b, 208 c, 210 a, 210 b, 210 c according to the second network configuration from the public blockchain node 214 a can be done in addition, overlaid on, or augment the first network configuration from the user device 204. In other embodiments, the configuring of the CSP nodes 208 a, 208 b, 208 c, 210 a, 210 b, 210 c according to the second network configuration from the public blockchain node 214 a can be done instead or replace the network configuration from the user device 204. Thus, the federated blockchain network that comprises the CSP nodes 208 a, 208 b, 208 c, 210 a, 210 b, 210 c can be called its private blockchain components and public blockchain nodes 214 a, 214 b, 214 c its public blockchain components. Thus, the federated blockchain network has the benefits of a decentralized architecture that spans not only public blockchain nodes 214 a, 214 b, 214 c but also CSP nodes (private blockchain nodes) 208 a, 208 b, 208 c, 210 a, 210 b, 210 c to mitigate its vulnerability to public cyberattacks. Further, the federated blockchain network has the benefits of regulating user access with access control lists such that its computational resources are not exhausted from utilization by too many users. In addition, the federated blockchain network comprises trusted CSP nodes as its private blockchain components as selected by the user 202.

In one or more embodiments, the user 202 utilizes the federated blockchain network from the user device 204. In further embodiments, the user 202 can provide an order (e.g. to perform secured transactions) for the federated blockchain network from the user device 204 to the access node 206. Further, the access node 206 can provide the order to each CSP node 208 a, 210 a and the public blockchain node 214 a. In addition, the CSP node 208 a can configure CSP nodes 208 a, 208 b, 208 c according to the order, the CSP node 210 a can configure CSP nodes 210 a, 210 b, 210 c according to the order, and the public blockchain node can configure the public blockchain nodes 214 a, 214 b, 214 c according to the order.

Referring to FIG. 2B, the system 215 depicts some of the actions performed by user device 204, access node 206, CSP node 208 a, 210 b, public server 212, and public blockchain node 214 a. In one or more embodiments, a user can select trusted CSPs (and a public blockchain) through a user interface on the user device 204 in configuring a federated blockchain network, which can include executing ((electronically) signing) master-slave agreements between itself, the steward entity operating the access node 206 and the selected CSPs 216. Further, the user, through the user device 204, can upload technical configurations 218 to the access node 206. The technical configurations can include a first network configuration for portions of the federated blockchain network as well as business network definitions, models, scripts, access control lists, and query files. In addition, the user, through the user device 204, can confirm and submits orders 220 for the federated blockchain network to the access node 206 to perform secured transactions.

In one or more embodiments, the access node 206 can instantiate or configure a master account for each selected CSP on itself and can instantiate or configure slave accounts for each selected CSP 222 (on CSP nodes 208 a, 210 a) according to the executed master-slave agreement received from the user device 204. Further, the access node 206 can provide an indication (via a message, notification, signal, etc.) 224 to each CSP node 208 a, 210 a to configure their respective CSP nodes as blockchain nodes for the federated blockchain network. The access node 206 can provide the first network configuration such that each CSP node 208 a, 210 a can configure their respective CSP nodes for the federated blockchain network according to the first network configuration. In addition, the access node 206 can generate first credentials and provide the first credentials 226 to the CSP node 208 a, 210 a so that the CSP nodes can configure their respective CSP nodes according to the first network configuration using the first credentials. Also, the access node 206 can provide an indication (via a message, notification, signal, etc.) 228 to each CSP node 208 a, 210 a for them to configure the port permissions for the respective CSP nodes. Port permissions are defined in a corresponding access control list.

In one or more embodiments, the access node 206 saves/stores the first credentials 230 on the public server 212. The saving/storing of the first credentials can trigger the public server 212 to provide an indication (via a message, notification, signal, etc.) to the public blockchain node 214 a to access the first credentials 232 from the public server 212 and to configure its respective public blockchain nodes according to its public blockchain smart contract. Further, the pubic blockchain smart contract can include or indicate a second network configuration to configure the respective public blockchain nodes as well as the CSP nodes that are used as part of the federated public blockchain network. In addition, the public blockchain smart contract can include instructions to use second credentials in configuring the second network configuration. Consequently, the public blockchain node 214 a can generate the second credentials 234.

In one or more embodiments, the public blockchain node 214 a can access 236 each CSP node 208 a, 210 a using the first credentials and send an indication (via a message, notification, signal, etc.) or instructions to each CSP node to adjust the first credentials to second credentials. The adjusting can include removing the first credentials and adding the second credentials. Further, the public blockchain node 214 a can provide the second network configuration 238 to each CSP node 208 a, 210 a such that each CSP node 208 a, 210 a can configure their respective CSP nodes according to the second network configuration using the second credentials. Also, the public blockchain node 214 a can provide to each CSP node 208 a, 210 a the network model, scripts, access control lists, and query definitions for the second network configuration 240. Once each CSP node configures their respective CSP nodes according to the second network configuration, then the user, through the user device 204, can interact (e.g. perform secured transactions) 242 with portions of the federated blockchain network including each CSP node 208 a, 210 a. The federated blockchain network comprises each CSP node and each configured public blockchain network configured according to the first network configuration and/or the second network configuration.

Referring to FIG. 2C, in one or more embodiments, the system 245 can comprise a user device 204 associated with a user 202 interacting with an access node 246. The access node 246 can interact with a public blockchain system 248 that initiates configuration of portions of a federated blockchain network according to a network configuration based on a public blockchain smart contract. The public blockchain system 248 can include a public server 250 and public blockchain nodes 252. Further, the public server 250 can include credentials 250 s for the federated blockchain network, certificates 250 b, blockchain binary libraries 250 c, models 250 d, scripts 250 e, access control lists 250 f, and query files 250 g. In addition, the public blockchain nodes 252 can include credentials 252 a for the federated blockchain network, certificates 252 b, CSP Command Line Interface (CLI) binary libraries 252 c, credential change logic 252 d, and instantiation (generation) logic 252 e for generating/configuring portions of the federated blockchain network. A certificate can be provided by a CSP so that the public server or public blockchain node can remotely login to provision a blockchain node of the CSP with the credentials. Blockchain binary libraries are core blockchain software that the user has chosen as their preferred way in which to the implement blockchain technology on the federated blockchain network (e.g. Hyperledger, Ethereum Enterprise, etc.). The CSP CLI ensures the smart contract can run CSP CLI commands. The credential change logic allows the request and the downloading of new credentials (and/or certificates) for server access because credentials hosted on public server are being passed from a proprietary system (CSP nodes) to public blockchain nodes that implement a smart contract. Instantiation Logic details programmatic steps in the form of an executable script, to remotely instantiate/configure blockchain nodes (e.g. Login to VM via SSH, change director to root directory, execute Hyperledger binaries, etc.).

In one or more embodiments, the system 245 can include CSP nodes 254, 262. The access node 246 can establish a master account 256, 264 for each CSP. Further, each CSP can have a slave organization or slave account 258 a, 258 b, 266 a, 266 b within each CSP 254, 262. Further, each slave organization 258 a, 258 b, 266 a, 266 b can have one or more blockchain nodes 260 a, 260 b, 268 a, 268 b, each including a ledger for their respective portion of the federated blockchain network to perform secured transactions. The intermediary entity operating the access node provides federated blockchain service to the user and contracts with CSPs through Master Service Agreements to re-sell/provision the federated blockchain service (e.g. x86 servers that act as blockchain nodes). In doing so, the intermediary entity provides prospective users the ability to provision a federated blockchain network that diversifies the trust across multiple CSPs (are chosen as the blockchain node providers). The intermediary entity in such embodiments, re-sells the federated blockchain services based on the MSAs to generate revenue. Because the intermediary entity holds the credentials and certificates to the provisioned CSP servers, the intermediary entity has access to all the CSP nodes of the federated blockchain network thereby no decentralization. A public blockchain smart contract is leveraged to autonomously request new certificates and change the passwords on all provisioned CSP servers in which one or more public blockchain nodes, according to the smart contract, has access to the federated blockchain network nodes. The smart contract is programmed to change the password and certificate of federated blockchain nodes. This effectively locks other actors from accessing the federated blockchain nodes and securing a trusted federated blockchain network. The federated blockchain network continues to persist as long as a user pays the usage rates to the intermediary entity providing the federated blockchain service.

FIG. 2D depicts an illustrative embodiment of a method 270 in accordance with various aspects described herein. In one or more embodiments, aspects of method 270 can be performed by a user device, access node, CSP node, public server, or public blockchain node as shown in FIG. 2A. The method 270 can include a user device, at 271, providing selected (trusted) CSPs to provide portions of the federated blockchain network then executing and transmitting the master-slave agreement for each selected CSP to the access node. In some embodiments, the user device can provide a selection of a public blockchain network to provide portions of the federated blockchain network. Further, the method 270 can include the access node, at 272, obtaining or receiving, from a user device, a master-slave agreement for each selected CSP, and, at 274, obtaining a first network configuration, from the user device, for the federated blockchain network. In addition, the method 270 can include the access node, at 276, generating first credentials for portions of the federated blockchain network. Also, the method 270 can include the access node, at 278, transmitting to a CSP node the first network configuration and the first credentials. In some embodiments, the first network configuration and the first credentials can be provided separately.

In one or more embodiments, the method 270 can include the CSP node, at 280, configuring a first group of blockchain nodes according to the first network configuration and the first credentials. Further, the method 270 can include the access node, at 282, transmitting the first credentials to a public server. In addition, the method 270 can include the public server, at 284, transmitting the first credentials and an indication to generate portions of the federated blockchain network to a public blockchain node. The indication can be a message, notification, signal, etc. Also, the method 270 can include the public blockchain node, at 286, configuring a second group of blockchain nodes according to a second network configuration based on a public blockchain smart contract. The federated blockchain network comprises the first group of blockchain nodes and the second group of blockchain nodes. Moreover, the first group of blockchain nodes comprise a group of CSP nodes, and the second group of blockchain nodes comprise a group of public blockchain nodes. Further, the method 270 can include the public blockchain node, at 288, transmitting the second network configuration to the CSP node. In addition, the method 270 can include the CSP node, at 290, configuring the first group of blockchain nodes according to the second network configuration.

In one or more embodiments, the public blockchain node can generate second credentials, and the configuring of the second group of blockchain nodes by the public blockchain node can comprise configuring the second group of blockchain nodes according to the second credentials. Further, the public blockchain node can transmit the second credentials with (or separately from) the second network configuration to the CSP node, and the CSP node configures the first group of blockchain nodes according to the second credentials and the second network configuration.

In one or more embodiments, once the federated blockchain network has been configured, the user, through the user device, can utilize the federated blockchain network to perform secured transactions. In further embodiments, the access node can receive, from the user device, an order (e.g. to perform a secured transaction) for the federated blockchain network and the access node can transmit the order to the CSP node and the public blockchain node. The CSP node can configure the first group of blockchain nodes according to the order and the public blockchain node can configure the second group of blockchain nodes according to the order.

In one or more embodiments, the public blockchain node can provide at least one of a network model, scripts, access control rules, and query definitions, and the CSP node can configure the first group of blockchain nodes according to at least one of the network model, scripts, access control rules, and query definitions.

In one or more embodiments, the CSP node can receive first credentials and a first network configuration from an access node for a federated blockchain network. The receipt of the first credentials and the first network configuration can be in one message or separate messages. Further, the CSP node can configure a first group of blockchain nodes according to the first network configuration. In addition, the CSP node can receive a second network configuration from a public blockchain node. Also, the CSP node can configure the first group of blockchain nodes according to the second network configuration. The public blockchain node can configure a second group of blockchain nodes according to the second network configuration. The federated blockchain network comprises the first group of blockchain nodes and the second group of blockchain nodes. In addition, the first group of blockchain nodes comprise a group of CSP nodes, and the second group of blockchain nodes comprise a group of public blockchain nodes.

In further embodiments, the CSP node can receive first instructions from the public blockchain node to adjust the first credentials to a second credentials and the CSP node can adjust the first credentials to the second credentials, accordingly. In addition, the configuring of the first group of blockchain nodes by the CSP node according to the second network configuration can comprise the CSP node configuring the first group of blockchain node according to the second network configuration and the second credentials. Also, the public blockchain node can generate second credentials and can use the second credentials in configuring the second group of blockchain nodes according to the second network configuration.

In additional embodiments, the access node can transmit the first credentials and the first network configuration in response to receiving a master-slave agreement from a user device for the CSP. Once the federated blockchain network has been configured, the user, through the user device, can utilize the federated blockchain network to perform secured transactions. That is, user input associated with the user from the user device provides instructions for the federated blockchain network to perform transactions. In further embodiments, the access node can receive, from the user device, an order (e.g. to perform a secured transaction) for the federated blockchain network and the access node can transmit the order to the CSP node and the public blockchain node. The CSP node can configure the first group of blockchain nodes according to the order and the public blockchain node can configure the second group of blockchain nodes according to the order. In other embodiments, the public blockchain node can provide at least one of a network model, scripts, access control rules, and query definitions, and the CSP node can configure the first group of blockchain nodes according to at least one of the network model, scripts, access control rules, and query definitions.

In one or more embodiments, the public blockchain node can receive an indication from a public server to generate a portion of a federated blockchain network according to a public blockchain smart contract. The indication can be a message, notification, signal, etc. Further, the public blockchain node can configure a first group of blockchain nodes according to a first network configuration based on the public blockchain smart contract. In addition, the public blockchain node can transmit the first network configuration to a CSP node. The CSP node can configure a second group of blockchain nodes according to the first network configuration. The federated blockchain network can comprise the first group of blockchain nodes and the second group of block chain nodes. Also, the first group of blockchain nodes comprise a group of public blockchain nodes, and the second group of blockchain nodes comprise a group of CSP nodes.

In further embodiments, the public blockchain node can obtain first credentials from the public server and can generate second credentials such that the configuring of the first group of blockchain nodes can comprise configuring the first group of blockchain nodes according to the second credentials. In additional embodiments, the public blockchain node can transmit the second credentials to the CSP node, and configuring of the second group of blockchain nodes by the CSP node can comprise configuring of the second group of blockchain nodes according to the second credentials.

While for purposes of simplicity of explanation, the respective processes are shown and described as a series of blocks in FIG. 2D, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks may occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Moreover, not all illustrated blocks may be required to implement the methods described herein.

Further, portions of embodiments can be combined with portions of other embodiments.

Referring now to FIG. 3, a block diagram 300 is shown illustrating an example, non-limiting embodiment of a virtualized communication network in accordance with various aspects described herein. In particular a virtualized communication network is presented that can be used to implement some or all of the subsystems and functions of communication network 100, the subsystems and functions of systems 200, 215, 245 and method 270 presented in FIGS. 1, 2A, 2B, 2C, 2D and 3. For example, virtualized communication network 300 can facilitate in whole or in part configuring CSP nodes and public blockchain nodes for a federated blockchain network.

In particular, a cloud networking architecture is shown that leverages cloud technologies and supports rapid innovation and scalability via a transport layer 350, a virtualized network function cloud 325 and/or one or more cloud computing environments 375. In various embodiments, this cloud networking architecture is an open architecture that leverages application programming interfaces (APIs); reduces complexity from services and operations; supports more nimble business models; and rapidly and seamlessly scales to meet evolving customer requirements including traffic growth, diversity of traffic types, and diversity of performance and reliability expectations.

In contrast to traditional network elements—which are typically integrated to perform a single function, the virtualized communication network employs virtual network elements (VNEs) 330, 332, 334, etc. that perform some or all of the functions of network elements 150, 152, 154, 156, etc. For example, the network architecture can provide a substrate of networking capability, often called Network Function Virtualization Infrastructure (NFVI) or simply infrastructure that is capable of being directed with software and Software Defined Networking (SDN) protocols to perform a broad variety of network functions and services. This infrastructure can include several types of substrates. The most typical type of substrate being servers that support Network Function Virtualization (NFV), followed by packet forwarding capabilities based on generic computing resources, with specialized network technologies brought to bear when general purpose processors or general purpose integrated circuit devices offered by merchants (referred to herein as merchant silicon) are not appropriate. In this case, communication services can be implemented as cloud-centric workloads.

As an example, a traditional network element 150 (shown in FIG. 1), such as an edge router can be implemented via a VNE 330 composed of NFV software modules, merchant silicon, and associated controllers. The software can be written so that increasing workload consumes incremental resources from a common resource pool, and moreover so that it's elastic: so the resources are only consumed when needed. In a similar fashion, other network elements such as other routers, switches, edge caches, and middle-boxes are instantiated from the common resource pool. Such sharing of infrastructure across a broad set of uses makes planning and growing infrastructure easier to manage.

In an embodiment, the transport layer 350 includes fiber, cable, wired and/or wireless transport elements, network elements and interfaces to provide broadband access 110, wireless access 120, voice access 130, media access 140 and/or access to content sources 175 for distribution of content to any or all of the access technologies. In particular, in some cases a network element needs to be positioned at a specific place, and this allows for less sharing of common infrastructure. Other times, the network elements have specific physical layer adapters that cannot be abstracted or virtualized, and might require special DSP code and analog front-ends (AFEs) that do not lend themselves to implementation as VNEs 330, 332 or 334. These network elements can be included in transport layer 350.

The virtualized network function cloud 325 interfaces with the transport layer 350 to provide the VNEs 330, 332, 334, etc. to provide specific NFVs. In particular, the virtualized network function cloud 325 leverages cloud operations, applications, and architectures to support networking workloads. The virtualized network elements 330, 332 and 334 can employ network function software that provides either a one-for-one mapping of traditional network element function or alternately some combination of network functions designed for cloud computing. For example, VNEs 330, 332 and 334 can include route reflectors, domain name system (DNS) servers, and dynamic host configuration protocol (DHCP) servers, system architecture evolution (SAE) and/or mobility management entity (MME) gateways, broadband network gateways, IP edge routers for IP-VPN, Ethernet and other services, load balancers, distributers and other network elements. Because these elements don't typically need to forward large amounts of traffic, their workload can be distributed across a number of servers—each of which adds a portion of the capability, and overall which creates an elastic function with higher availability than its former monolithic version. These virtual network elements 330, 332, 334, etc. can be instantiated and managed using an orchestration approach similar to those used in cloud compute services.

The cloud computing environments 375 can interface with the virtualized network function cloud 325 via APIs that expose functional capabilities of the VNEs 330, 332, 334, etc. to provide the flexible and expanded capabilities to the virtualized network function cloud 325. In particular, network workloads may have applications distributed across the virtualized network function cloud 325 and cloud computing environment 375 and in the commercial cloud, or might simply orchestrate workloads supported entirely in NFV infrastructure from these third party locations.

Turning now to FIG. 4, there is illustrated a block diagram of a computing environment in accordance with various aspects described herein. In order to provide additional context for various embodiments of the embodiments described herein, FIG. 4 and the following discussion are intended to provide a brief, general description of a suitable computing environment 400 in which the various embodiments of the subject disclosure can be implemented. In particular, computing environment 400 can be used in the implementation of network elements 150, 152, 154, 156, access terminal 112, base station or access point 122, switching device 132, media terminal 142, and/or VNEs 330, 332, 334, etc. Each of these devices can be implemented via computer-executable instructions that can run on one or more computers, and/or in combination with other program modules and/or as a combination of hardware and software. For example, computing environment 400 can facilitate in whole or in part configuring CSP nodes and public blockchain nodes for a federated blockchain network. Further, the user device, access node, CSP nodes, public server, and public blockchain nodes can comprise the computing environment 400.

Generally, program modules comprise routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the methods can be practiced with other computer system configurations, comprising single-processor or multiprocessor computer systems, minicomputers, mainframe computers, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices.

As used herein, a processing circuit includes one or more processors as well as other application specific circuits such as an application specific integrated circuit, digital logic circuit, state machine, programmable gate array or other circuit that processes input signals or data and that produces output signals or data in response thereto. It should be noted that while any functions and features described herein in association with the operation of a processor could likewise be performed by a processing circuit.

The illustrated embodiments of the embodiments herein can be also practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

Computing devices typically comprise a variety of media, which can comprise computer-readable storage media and/or communications media, which two terms are used herein differently from one another as follows. Computer-readable storage media can be any available storage media that can be accessed by the computer and comprises both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable storage media can be implemented in connection with any method or technology for storage of information such as computer-readable instructions, program modules, structured data or unstructured data.

Computer-readable storage media can comprise, but are not limited to, random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or other tangible and/or non-transitory media which can be used to store desired information. In this regard, the terms “tangible” or “non-transitory” herein as applied to storage, memory or computer-readable media, are to be understood to exclude only propagating transitory signals per se as modifiers and do not relinquish rights to all standard storage, memory or computer-readable media that are not only propagating transitory signals per se.

Computer-readable storage media can be accessed by one or more local or remote computing devices, e.g., via access requests, queries or other data retrieval protocols, for a variety of operations with respect to the information stored by the medium.

Communications media typically embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and comprises any information delivery or transport media. The term “modulated data signal” or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals. By way of example, and not limitation, communication media comprise wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

With reference again to FIG. 4, the example environment can comprise a computer 402, the computer 402 comprising a processing unit 404, a system memory 406 and a system bus 408. The system bus 408 couples system components including, but not limited to, the system memory 406 to the processing unit 404. The processing unit 404 can be any of various commercially available processors. Dual microprocessors and other multiprocessor architectures can also be employed as the processing unit 404.

The system bus 408 can be any of several types of bus structure that can further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory 406 comprises ROM 410 and RAM 412. A basic input/output system (BIOS) can be stored in a non-volatile memory such as ROM, erasable programmable read only memory (EPROM), EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer 402, such as during startup. The RAM 412 can also comprise a high-speed RAM such as static RAM for caching data.

The computer 402 further comprises an internal hard disk drive (HDD) 414 (e.g., EIDE, SATA), which internal HDD 414 can also be configured for external use in a suitable chassis (not shown), a magnetic floppy disk drive (FDD) 416, (e.g., to read from or write to a removable diskette 418) and an optical disk drive 420, (e.g., reading a CD-ROM disk 422 or, to read from or write to other high capacity optical media such as the DVD). The HDD 414, magnetic FDD 416 and optical disk drive 420 can be connected to the system bus 408 by a hard disk drive interface 424, a magnetic disk drive interface 426 and an optical drive interface 428, respectively. The hard disk drive interface 424 for external drive implementations comprises at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE) 1394 interface technologies. Other external drive connection technologies are within contemplation of the embodiments described herein.

The drives and their associated computer-readable storage media provide nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For the computer 402, the drives and storage media accommodate the storage of any data in a suitable digital format. Although the description of computer-readable storage media above refers to a hard disk drive (HDD), a removable magnetic diskette, and a removable optical media such as a CD or DVD, it should be appreciated by those skilled in the art that other types of storage media which are readable by a computer, such as zip drives, magnetic cassettes, flash memory cards, cartridges, and the like, can also be used in the example operating environment, and further, that any such storage media can contain computer-executable instructions for performing the methods described herein.

A number of program modules can be stored in the drives and RAM 412, comprising an operating system 430, one or more application programs 432, other program modules 434 and program data 436. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM 412. The systems and methods described herein can be implemented utilizing various commercially available operating systems or combinations of operating systems.

A user can enter commands and information into the computer 402 through one or more wired/wireless input devices, e.g., a keyboard 438 and a pointing device, such as a mouse 440. Other input devices (not shown) can comprise a microphone, an infrared (IR) remote control, a joystick, a game pad, a stylus pen, touch screen or the like. These and other input devices are often connected to the processing unit 404 through an input device interface 442 that can be coupled to the system bus 408, but can be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a universal serial bus (USB) port, an IR interface, etc.

A monitor 444 or other type of display device can be also connected to the system bus 408 via an interface, such as a video adapter 446. It will also be appreciated that in alternative embodiments, a monitor 444 can also be any display device (e.g., another computer having a display, a smart phone, a tablet computer, etc.) for receiving display information associated with computer 402 via any communication means, including via the Internet and cloud-based networks. In addition to the monitor 444, a computer typically comprises other peripheral output devices (not shown), such as speakers, printers, etc.

The computer 402 can operate in a networked environment using logical connections via wired and/or wireless communications to one or more remote computers, such as a remote computer(s) 448. The remote computer(s) 448 can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically comprises many or all of the elements described relative to the computer 402, although, for purposes of brevity, only a remote memory/storage device 450 is illustrated. The logical connections depicted comprise wired/wireless connectivity to a local area network (LAN) 452 and/or larger networks, e.g., a wide area network (WAN) 454. Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which can connect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer 402 can be connected to the LAN 452 through a wired and/or wireless communication network interface or adapter 456. The adapter 456 can facilitate wired or wireless communication to the LAN 452, which can also comprise a wireless AP disposed thereon for communicating with the adapter 456.

When used in a WAN networking environment, the computer 402 can comprise a modem 458 or can be connected to a communications server on the WAN 454 or has other means for establishing communications over the WAN 454, such as by way of the Internet. The modem 458, which can be internal or external and a wired or wireless device, can be connected to the system bus 408 via the input device interface 442. In a networked environment, program modules depicted relative to the computer 402 or portions thereof, can be stored in the remote memory/storage device 450. It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers can be used.

The computer 402 can be operable to communicate with any wireless devices or entities operatively disposed in wireless communication, e.g., a printer, scanner, desktop and/or portable computer, portable data assistant, communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, restroom), and telephone. This can comprise Wireless Fidelity (Wi-Fi) and BLUETOOTH® wireless technologies. Thus, the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices.

Wi-Fi can allow connection to the Internet from a couch at home, a bed in a hotel room or a conference room at work, without wires. Wi-Fi is a wireless technology similar to that used in a cell phone that enables such devices, e.g., computers, to send and receive data indoors and out; anywhere within the range of a base station. Wi-Fi networks use radio technologies called IEEE 802.11 (a, b, g, n, ac, ag, etc.) to provide secure, reliable, fast wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to wired networks (which can use IEEE 802.3 or Ethernet). Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands for example or with products that contain both bands (dual band), so the networks can provide real-world performance similar to the basic 10BaseT wired Ethernet networks used in many offices.

Turning now to FIG. 5, an embodiment 500 of a mobile network platform 510 is shown that is an example of network elements 150, 152, 154, 156, and/or VNEs 330, 332, 334, etc. For example, platform 510 can facilitate in whole or in part configuring CSP nodes and public blockchain nodes for a federated blockchain network. In one or more embodiments, the mobile network platform 510 can generate and receive signals transmitted and received by base stations or access points such as base station or access point 122. Generally, mobile network platform 510 can comprise components, e.g., nodes, gateways, interfaces, servers, or disparate platforms, that facilitate both packet-switched (PS) (e.g., internet protocol (IP), frame relay, asynchronous transfer mode (ATM)) and circuit-switched (CS) traffic (e.g., voice and data), as well as control generation for networked wireless telecommunication. As a non-limiting example, mobile network platform 510 can be included in telecommunications carrier networks, and can be considered carrier-side components as discussed elsewhere herein. Mobile network platform 510 comprises CS gateway node(s) 512 which can interface CS traffic received from legacy networks like telephony network(s) 540 (e.g., public switched telephone network (PSTN), or public land mobile network (PLMN)) or a signaling system #7 (SS7) network 560. CS gateway node(s) 512 can authorize and authenticate traffic (e.g., voice) arising from such networks. Additionally, CS gateway node(s) 512 can access mobility, or roaming, data generated through SS7 network 560; for instance, mobility data stored in a visited location register (VLR), which can reside in memory 530. Moreover, CS gateway node(s) 512 interfaces CS-based traffic and signaling and PS gateway node(s) 518. As an example, in a 3GPP UMTS network, CS gateway node(s) 512 can be realized at least in part in gateway GPRS support node(s) (GGSN). It should be appreciated that functionality and specific operation of CS gateway node(s) 512, PS gateway node(s) 518, and serving node(s) 516, is provided and dictated by radio technology(ies) utilized by mobile network platform 510 for telecommunication over a radio access network 520 with other devices, such as a radiotelephone 575.

In addition to receiving and processing CS-switched traffic and signaling, PS gateway node(s) 518 can authorize and authenticate PS-based data sessions with served mobile devices. Data sessions can comprise traffic, or content(s), exchanged with networks external to the mobile network platform 510, like wide area network(s) (WANs) 550, enterprise network(s) 570, and service network(s) 580, which can be embodied in local area network(s) (LANs), can also be interfaced with mobile network platform 510 through PS gateway node(s) 518. It is to be noted that WANs 550 and enterprise network(s) 570 can embody, at least in part, a service network(s) like IP multimedia subsystem (IMS). Based on radio technology layer(s) available in technology resource(s) or radio access network 520, PS gateway node(s) 518 can generate packet data protocol contexts when a data session is established; other data structures that facilitate routing of packetized data also can be generated. To that end, in an aspect, PS gateway node(s) 518 can comprise a tunnel interface (e.g., tunnel termination gateway (TTG) in 3GPP UMTS network(s) (not shown)) which can facilitate packetized communication with disparate wireless network(s), such as Wi-Fi networks.

In embodiment 500, mobile network platform 510 also comprises serving node(s) 516 that, based upon available radio technology layer(s) within technology resource(s) in the radio access network 520, convey the various packetized flows of data streams received through PS gateway node(s) 518. It is to be noted that for technology resource(s) that rely primarily on CS communication, server node(s) can deliver traffic without reliance on PS gateway node(s) 518; for example, server node(s) can embody at least in part a mobile switching center. As an example, in a 3GPP UMTS network, serving node(s) 516 can be embodied in serving GPRS support node(s) (SGSN).

For radio technologies that exploit packetized communication, server(s) 514 in mobile network platform 510 can execute numerous applications that can generate multiple disparate packetized data streams or flows, and manage (e.g., schedule, queue, format . . . ) such flows. Such application(s) can comprise add-on features to standard services (for example, provisioning, billing, customer support . . . ) provided by mobile network platform 510. Data streams (e.g., content(s) that are part of a voice call or data session) can be conveyed to PS gateway node(s) 518 for authorization/authentication and initiation of a data session, and to serving node(s) 516 for communication thereafter. In addition to application server, server(s) 514 can comprise utility server(s), a utility server can comprise a provisioning server, an operations and maintenance server, a security server that can implement at least in part a certificate authority and firewalls as well as other security mechanisms, and the like. In an aspect, security server(s) secure communication served through mobile network platform 510 to ensure network's operation and data integrity in addition to authorization and authentication procedures that CS gateway node(s) 512 and PS gateway node(s) 518 can enact. Moreover, provisioning server(s) can provision services from external network(s) like networks operated by a disparate service provider; for instance, WAN 550 or Global Positioning System (GPS) network(s) (not shown). Provisioning server(s) can also provision coverage through networks associated to mobile network platform 510 (e.g., deployed and operated by the same service provider), such as the distributed antennas networks shown in FIG. 1(s) that enhance wireless service coverage by providing more network coverage.

It is to be noted that server(s) 514 can comprise one or more processors configured to confer at least in part the functionality of mobile network platform 510. To that end, the one or more processor can execute code instructions stored in memory 530, for example. It is should be appreciated that server(s) 514 can comprise a content manager, which operates in substantially the same manner as described hereinbefore.

In example embodiment 500, memory 530 can store information related to operation of mobile network platform 510. Other operational information can comprise provisioning information of mobile devices served through mobile network platform 510, subscriber databases; application intelligence, pricing schemes, e.g., promotional rates, flat-rate programs, couponing campaigns; technical specification(s) consistent with telecommunication protocols for operation of disparate radio, or wireless, technology layers; and so forth. Memory 530 can also store information from at least one of telephony network(s) 540, WAN 550, SS7 network 560, or enterprise network(s) 570. In an aspect, memory 530 can be, for example, accessed as part of a data store component or as a remotely connected memory store.

In order to provide a context for the various aspects of the disclosed subject matter, FIG. 5, and the following discussion, are intended to provide a brief, general description of a suitable environment in which the various aspects of the disclosed subject matter can be implemented. While the subject matter has been described above in the general context of computer-executable instructions of a computer program that runs on a computer and/or computers, those skilled in the art will recognize that the disclosed subject matter also can be implemented in combination with other program modules. Generally, program modules comprise routines, programs, components, data structures, etc. that perform particular tasks and/or implement particular abstract data types.

Turning now to FIG. 6, an illustrative embodiment of a communication device 600 is shown. The communication device 600 can serve as an illustrative embodiment of devices such as data terminals 114, mobile devices 124, vehicle 126, display devices 144 or other client devices for communication via either communications network 125. For example, computing device 600 can facilitate in whole or in part configuring CSP nodes and public blockchain nodes for a federated blockchain network. Further, the user device, access node, CSP nodes, public server, and public blockchain nodes can comprise the computing device 600.

The communication device 600 can comprise a wireline and/or wireless transceiver 602 (herein transceiver 602), a user interface (UI) 604, a power supply 614, a location receiver 616, a motion sensor 618, an orientation sensor 620, and a controller 606 for managing operations thereof. The transceiver 602 can support short-range or long-range wireless access technologies such as Bluetooth®, ZigBee®, WiFi, DECT, or cellular communication technologies, just to mention a few (Bluetooth® and ZigBee® are trademarks registered by the Bluetooth® Special Interest Group and the ZigBee® Alliance, respectively). Cellular technologies can include, for example, CDMA-1X, UMTS/HSDPA, GSM/GPRS, TDMA/EDGE, EV/DO, WiMAX, SDR, LTE, as well as other next generation wireless communication technologies as they arise. The transceiver 602 can also be adapted to support circuit-switched wireline access technologies (such as PSTN), packet-switched wireline access technologies (such as TCP/IP, VoIP, etc.), and combinations thereof.

The UI 604 can include a depressible or touch-sensitive keypad 608 with a navigation mechanism such as a roller ball, a joystick, a mouse, or a navigation disk for manipulating operations of the communication device 600. The keypad 608 can be an integral part of a housing assembly of the communication device 600 or an independent device operably coupled thereto by a tethered wireline interface (such as a USB cable) or a wireless interface supporting for example Bluetooth®. The keypad 608 can represent a numeric keypad commonly used by phones, and/or a QWERTY keypad with alphanumeric keys. The UI 604 can further include a display 610 such as monochrome or color LCD (Liquid Crystal Display), OLED (Organic Light Emitting Diode) or other suitable display technology for conveying images to an end user of the communication device 600. In an embodiment where the display 610 is touch-sensitive, a portion or all of the keypad 608 can be presented by way of the display 610 with navigation features.

The display 610 can use touch screen technology to also serve as a user interface for detecting user input. As a touch screen display, the communication device 600 can be adapted to present a user interface having graphical user interface (GUI) elements that can be selected by a user with a touch of a finger. The display 610 can be equipped with capacitive, resistive or other forms of sensing technology to detect how much surface area of a user's finger has been placed on a portion of the touch screen display. This sensing information can be used to control the manipulation of the GUI elements or other functions of the user interface. The display 610 can be an integral part of the housing assembly of the communication device 600 or an independent device communicatively coupled thereto by a tethered wireline interface (such as a cable) or a wireless interface.

The UI 604 can also include an audio system 612 that utilizes audio technology for conveying low volume audio (such as audio heard in proximity of a human ear) and high volume audio (such as speakerphone for hands free operation). The audio system 612 can further include a microphone for receiving audible signals of an end user. The audio system 612 can also be used for voice recognition applications. The UI 604 can further include an image sensor 613 such as a charged coupled device (CCD) camera for capturing still or moving images.

The power supply 614 can utilize common power management technologies such as replaceable and rechargeable batteries, supply regulation technologies, and/or charging system technologies for supplying energy to the components of the communication device 600 to facilitate long-range or short-range portable communications. Alternatively, or in combination, the charging system can utilize external power sources such as DC power supplied over a physical interface such as a USB port or other suitable tethering technologies.

The location receiver 616 can utilize location technology such as a global positioning system (GPS) receiver capable of assisted GPS for identifying a location of the communication device 600 based on signals generated by a constellation of GPS satellites, which can be used for facilitating location services such as navigation. The motion sensor 618 can utilize motion sensing technology such as an accelerometer, a gyroscope, or other suitable motion sensing technology to detect motion of the communication device 600 in three-dimensional space. The orientation sensor 620 can utilize orientation sensing technology such as a magnetometer to detect the orientation of the communication device 600 (north, south, west, and east, as well as combined orientations in degrees, minutes, or other suitable orientation metrics).

The communication device 600 can use the transceiver 602 to also determine a proximity to a cellular, WiFi, Bluetooth®, or other wireless access points by sensing techniques such as utilizing a received signal strength indicator (RSSI) and/or signal time of arrival (TOA) or time of flight (TOF) measurements. The controller 606 can utilize computing technologies such as a microprocessor, a digital signal processor (DSP), programmable gate arrays, application specific integrated circuits, and/or a video processor with associated storage memory such as Flash, ROM, RAM, SRAM, DRAM or other storage technologies for executing computer instructions, controlling, and processing data supplied by the aforementioned components of the communication device 600.

Other components not shown in FIG. 6 can be used in one or more embodiments of the subject disclosure. For instance, the communication device 600 can include a slot for adding or removing an identity module such as a Subscriber Identity Module (SIM) card or Universal Integrated Circuit Card (UICC). SIM or UICC cards can be used for identifying subscriber services, executing programs, storing subscriber data, and so on.

The terms “first,” “second,” “third,” and so forth, as used in the claims, unless otherwise clear by context, is for clarity only and doesn't otherwise indicate or imply any order in time. For instance, “a first determination,” “a second determination,” and “a third determination,” does not indicate or imply that the first determination is to be made before the second determination, or vice versa, etc.

In the subject specification, terms such as “store,” “storage,” “data store,” data storage,” “database,” and substantially any other information storage component relevant to operation and functionality of a component, refer to “memory components,” or entities embodied in a “memory” or components comprising the memory. It will be appreciated that the memory components described herein can be either volatile memory or nonvolatile memory, or can comprise both volatile and nonvolatile memory, by way of illustration, and not limitation, volatile memory, non-volatile memory, disk storage, and memory storage. Further, nonvolatile memory can be included in read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory can comprise random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM). Additionally, the disclosed memory components of systems or methods herein are intended to comprise, without being limited to comprising, these and any other suitable types of memory.

Moreover, it will be noted that the disclosed subject matter can be practiced with other computer system configurations, comprising single-processor or multiprocessor computer systems, mini-computing devices, mainframe computers, as well as personal computers, hand-held computing devices (e.g., PDA, phone, smartphone, watch, tablet computers, netbook computers, etc.), microprocessor-based or programmable consumer or industrial electronics, and the like. The illustrated aspects can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network; however, some if not all aspects of the subject disclosure can be practiced on stand-alone computers. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

In one or more embodiments, information regarding use of services can be generated including services being accessed, media consumption history, user preferences, and so forth. This information can be obtained by various methods including user input, detecting types of communications (e.g., video content vs. audio content), analysis of content streams, sampling, and so forth. The generating, obtaining and/or monitoring of this information can be responsive to an authorization provided by the user. In one or more embodiments, an analysis of data can be subject to authorization from user(s) associated with the data, such as an opt-in, an opt-out, acknowledgement requirements, notifications, selective authorization based on types of data, and so forth.

Some of the embodiments described herein can also employ artificial intelligence (AI) to facilitate automating one or more features described herein. The embodiments (e.g., in connection with automatically identifying acquired cell sites that provide a maximum value/benefit after addition to an existing communication network) can employ various AI-based schemes for carrying out various embodiments thereof. Moreover, the classifier can be employed to determine a ranking or priority of each cell site of the acquired network. A classifier is a function that maps an input attribute vector, x=(x1, x2, x3, x4, . . . , xn), to a confidence that the input belongs to a class, that is, f(x)=confidence (class). Such classification can employ a probabilistic and/or statistical-based analysis (e.g., factoring into the analysis utilities and costs) to determine or infer an action that a user desires to be automatically performed. A support vector machine (SVM) is an example of a classifier that can be employed. The SVM operates by finding a hypersurface in the space of possible inputs, which the hypersurface attempts to split the triggering criteria from the non-triggering events. Intuitively, this makes the classification correct for testing data that is near, but not identical to training data. Other directed and undirected model classification approaches comprise, e.g., naïve Bayes, Bayesian networks, decision trees, neural networks, fuzzy logic models, and probabilistic classification models providing different patterns of independence can be employed. Classification as used herein also is inclusive of statistical regression that is utilized to develop models of priority.

As will be readily appreciated, one or more of the embodiments can employ classifiers that are explicitly trained (e.g., via a generic training data) as well as implicitly trained (e.g., via observing UE behavior, operator preferences, historical information, receiving extrinsic information). For example, SVMs can be configured via a learning or training phase within a classifier constructor and feature selection module. Thus, the classifier(s) can be used to automatically learn and perform a number of functions, including but not limited to determining according to predetermined criteria which of the acquired cell sites will benefit a maximum number of subscribers and/or which of the acquired cell sites will add minimum value to the existing communication network coverage, etc.

As used in some contexts in this application, in some embodiments, the terms “component,” “system” and the like are intended to refer to, or comprise, a computer-related entity or an entity related to an operational apparatus with one or more specific functionalities, wherein the entity can be either hardware, a combination of hardware and software, software, or software in execution. As an example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, computer-executable instructions, a program, and/or a computer. By way of illustration and not limitation, both an application running on a server and the server can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems via the signal). As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, which is operated by a software or firmware application executed by a processor, wherein the processor can be internal or external to the apparatus and executes at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts, the electronic components can comprise a processor therein to execute software or firmware that confers at least in part the functionality of the electronic components. While various components have been illustrated as separate components, it will be appreciated that multiple components can be implemented as a single component, or a single component can be implemented as multiple components, without departing from example embodiments.

Further, the various embodiments can be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware or any combination thereof to control a computer to implement the disclosed subject matter. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device or computer-readable storage/communications media. For example, computer readable storage media can include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips), optical disks (e.g., compact disk (CD), digital versatile disk (DVD)), smart cards, and flash memory devices (e.g., card, stick, key drive). Of course, those skilled in the art will recognize many modifications can be made to this configuration without departing from the scope or spirit of the various embodiments.

In addition, the words “example” and “exemplary” are used herein to mean serving as an instance or illustration. Any embodiment or design described herein as “example” or “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word example or exemplary is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.

Moreover, terms such as “user equipment,” “mobile station,” “mobile,” subscriber station,” “access terminal,” “terminal,” “handset,” “mobile device” (and/or terms representing similar terminology) can refer to a wireless device utilized by a subscriber or user of a wireless communication service to receive or convey data, control, voice, video, sound, gaming or substantially any data-stream or signaling-stream. The foregoing terms are utilized interchangeably herein and with reference to the related drawings.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer” and the like are employed interchangeably throughout, unless context warrants particular distinctions among the terms. It should be appreciated that such terms can refer to human entities or automated components supported through artificial intelligence (e.g., a capacity to make inference based, at least, on complex mathematical formalisms), which can provide simulated vision, sound recognition and so forth.

As employed herein, the term “processor” can refer to substantially any computing processing unit or device comprising, but not limited to comprising, single-core processors; single-processors with software multithread execution capability; multi-core processors; multi-core processors with software multithread execution capability; multi-core processors with hardware multithread technology; parallel platforms; and parallel platforms with distributed shared memory. Additionally, a processor can refer to an integrated circuit, an application specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic controller (PLC), a complex programmable logic device (CPLD), a discrete gate or transistor logic, discrete hardware components or any combination thereof designed to perform the functions described herein. Processors can exploit nano-scale architectures such as, but not limited to, molecular and quantum-dot based transistors, switches and gates, in order to optimize space usage or enhance performance of user equipment. A processor can also be implemented as a combination of computing processing units.

As used herein, terms such as “data storage,” data storage,” “database,” and substantially any other information storage component relevant to operation and functionality of a component, refer to “memory components,” or entities embodied in a “memory” or components comprising the memory. It will be appreciated that the memory components or computer-readable storage media, described herein can be either volatile memory or nonvolatile memory or can include both volatile and nonvolatile memory.

What has been described above includes mere examples of various embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing these examples, but one of ordinary skill in the art can recognize that many further combinations and permutations of the present embodiments are possible. Accordingly, the embodiments disclosed and/or claimed herein are intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.

In addition, a flow diagram may include a “start” and/or “continue” indication. The “start” and “continue” indications reflect that the steps presented can optionally be incorporated in or otherwise used in conjunction with other routines. In this context, “start” indicates the beginning of the first step presented and may be preceded by other activities not specifically shown. Further, the “continue” indication reflects that the steps presented may be performed multiple times and/or may be succeeded by other activities not specifically shown. Further, while a flow diagram indicates a particular ordering of steps, other orderings are likewise possible provided that the principles of causality are maintained.

As may also be used herein, the term(s) “operably coupled to”, “coupled to”, and/or “coupling” includes direct coupling between items and/or indirect coupling between items via one or more intervening items. Such items and intervening items include, but are not limited to, junctions, communication paths, components, circuit elements, circuits, functional blocks, and/or devices. As an example of indirect coupling, a signal conveyed from a first item to a second item may be modified by one or more intervening items by modifying the form, nature or format of information in a signal, while one or more elements of the information in the signal are nevertheless conveyed in a manner than can be recognized by the second item. In a further example of indirect coupling, an action in a first item can cause a reaction on the second item, as a result of actions and/or reactions in one or more intervening items.

Although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement which achieves the same or similar purpose may be substituted for the embodiments described or shown by the subject disclosure. The subject disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, can be used in the subject disclosure. For instance, one or more features from one or more embodiments can be combined with one or more features of one or more other embodiments. In one or more embodiments, features that are positively recited can also be negatively recited and excluded from the embodiment with or without replacement by another structural and/or functional feature. The steps or functions described with respect to the embodiments of the subject disclosure can be performed in any order. The steps or functions described with respect to the embodiments of the subject disclosure can be performed alone or in combination with other steps or functions of the subject disclosure, as well as from other embodiments or from other steps that have not been described in the subject disclosure. Further, more than or less than all of the features described with respect to an embodiment can also be utilized. 

What is claimed is:
 1. A method, comprising: obtaining, by a processing system including a processor, from a user device, a master-slave agreement for a federated blockchain network and obtaining, by the processing system, a first network configuration for the federated blockchain network; transmitting, by the processing system, to a cloud service provider (CSP) node, the first network configuration; generating, by the processing system, first credentials; transmitting, by the processing system, the first credentials to the CSP node, wherein the CSP node configures a first group of blockchain nodes according to the first network configuration and the first credentials; and transmitting, by the processing system, the first credentials to a public server, wherein the public server sends, to a public blockchain node, the first credentials and an indication to generate a portion of the federated blockchain network, wherein the public blockchain node configures a second group of blockchain nodes according to a second network configuration based on a public blockchain smart contract, wherein the federated blockchain network comprises the first group of blockchain nodes and the second group of blockchain nodes.
 2. The method of claim 1, wherein the first group of blockchain nodes comprises a group of CSP nodes, wherein the second group of blockchain nodes comprises a group of public blockchain nodes.
 3. The method of claim 1, wherein the public blockchain node generates second credentials, wherein the configuring of the second group of blockchain nodes by the public blockchain node comprises configuring the second group of blockchain nodes according to the second credentials.
 4. The method of claim 3, wherein the public blockchain node transmits the second credentials and the second network configuration to the CSP node, wherein the CSP node configures the first group of blockchain nodes according to the second credentials and the second network configuration.
 5. The method of claim 1, wherein user input associated with the user from the user device provides instructions for the federated blockchain network to perform transactions.
 6. The method of claim 1, comprising receiving, by the processing system, from the user device, an order for the federated blockchain network; and transmitting, by the processing system, the order to the CSP node and the public blockchain node, wherein the CSP node configures the first group of blockchain nodes according to the order and the public blockchain node configures the second group of blockchain nodes according to the order.
 7. The method of claim 1, wherein the public blockchain node provides at least one of a network model, scripts, access control rules, and query definitions to the CSP node, wherein the CSP node configures the first group of blockchain nodes according to the at least one of the network model, scripts, access control rules, and query definitions.
 8. A device, comprising: a processing system including a processor; and a memory that stores executable instructions that, when executed by the processing system, facilitate performance of operations, the operations comprising: receiving first credentials and receiving a first network configuration from an access node for a federated blockchain network; configuring a first group of blockchain nodes according to the first network configuration; receiving a second network configuration from a public blockchain node; and configuring the first group of blockchain nodes according to the second network configuration, wherein the public blockchain node configures a second group of blockchain nodes according to the second network configuration, wherein the federated blockchain network comprises the first group of blockchain nodes and the second group of blockchain nodes.
 9. The device of claim 8, wherein the first group of blockchain nodes comprises a group of CSP nodes, wherein the second group of blockchain nodes comprises a group of public blockchain nodes.
 10. The device of claim 8, wherein the operations comprise: receiving first instructions from the public blockchain node to adjust the first credentials to a second credentials; and adjusting the first credentials to the second credentials.
 11. The device of claim 10, wherein the configuring of the first group of blockchain nodes according to the second network configuration comprises configuring the first group of blockchain node according to the second network configuration and the second credentials.
 12. The device of claim 8, wherein the public blockchain node generates second credentials and uses the second credentials in configuring the second group of blockchain nodes according to the second network configuration.
 13. The device of claim 8, wherein the access node transmits the first credentials and the first network configuration in response to receiving a master-slave agreement from a user device.
 14. The device of claim 8, wherein user input associated with the user from the user device provides instructions for the federated blockchain network to perform transactions.
 15. The device of claim 8, wherein the operations comprise: receiving an order from the access node; and configuring the first group of blockchain nodes according to the order.
 16. The device of claim 8, wherein the operations comprise: receiving at least one of a network model, scripts, access control rules, and query definitions from the public blockchain node; and configuring the first group of blockchain nodes according to the at least one of the network model, scripts, access control rules, and query definitions.
 17. A machine-readable storage device, comprising executable instructions that, when executed by a processing system including a processor, facilitate performance of operations comprising: receiving an indication from a public server to generate a portion of a federated blockchain network according to a public blockchain smart contract; configuring a first group of blockchain nodes according to a first network configuration based on the public blockchain smart contract; and transmitting the first network configuration to a cloud service provider (CSP) node, wherein the CSP node configures a second group of blockchain nodes according to the first network configuration, wherein the federated blockchain network comprises the first group of blockchain nodes and the second group of block chain nodes.
 18. The machine-readable storage device of claim 17, wherein the first group of blockchain nodes comprise a group of public blockchain nodes, wherein the second group of blockchain nodes comprise a group of CSP nodes.
 19. The machine-readable storage device of claim 17, wherein the operations comprise: obtaining first credentials from the public server; and generating second credentials, wherein the configuring of the first group of blockchain nodes comprises configuring the first group of blockchain nodes according to the second credentials.
 20. The machine-readable storage device of claim 19, wherein the operations comprise transmitting the second credentials to the CSP node, wherein configuring of the second group of blockchain nodes by the CSP node comprise configuring of the second group of blockchain nodes according to the second credentials. 